Apparatus, system and method of multi-user wireless communication

ABSTRACT

Some demonstrative embodiments include apparatuses, devices, systems and methods of multi-user (MU) wireless communication. For example, a wireless station may be configured to generate a MU Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) including a header field and a plurality of Media Access Control (MAC) Protocol Data Units (MPDUs) to a respective plurality of users, the header field including an indication of a plurality of lengths of respective ones of the plurality of MPDUs, one or more MPDUs of the plurality of MPDUs being followed by one or more respective PHY padding portions extending to an end of a longest MPDU of the plurality of MPDUs; and process transmission of the MU PPDU to the plurality of users over a wireless communication band.

CROSS REFERENCE

This application claims the benefit of and priority from U.S.Provisional Patent Application No. 62/154,893 entitled “Apparatus,System and Method of Multi-User Wireless Communication”, filed Apr. 30,2015, the entire disclosure of which is incorporated herein byreference.

TECHNICAL FIELD

Embodiments described herein generally relate to multi-user (MU)wireless communication.

BACKGROUND

A wireless communication network in a millimeter-wave band may providehigh-speed data access for users of wireless communication devices.

According to some Specifications and/or Protocols, devices may beconfigured to perform all transmissions and receptions over a singlechannel bandwidth (BW).

Some Specifications, e.g., an IEEE 802.11ad Specification, may beconfigured to support a Single User (SU) system, in which a Station(STA) cannot transmit frames to more than a single STA at a time.

BRIEF DESCRIPTION OF THE DRAWINGS

For simplicity and clarity of illustration, elements shown in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements may be exaggerated relative to otherelements for clarity of presentation. Furthermore, reference numeralsmay be repeated among the figures to indicate corresponding or analogouselements. The figures are listed below.

FIG. 1 is a schematic block diagram illustration of a system, inaccordance with some demonstrative embodiments.

FIG. 2 is a schematic illustration of a Multi-User (MU) scheme includingtwo groups of Stations (STAs), in accordance with some demonstrativeembodiments.

FIG. 3 is a schematic illustration of a Physical Layer ConvergenceProtocol (PLCP) Protocol Data Unit (PPDU) structure, in accordance withsome demonstrative embodiments.

FIG. 4 is a schematic illustration of a MU PPDU structure using MediaAccess Control (MAC) padding.

FIG. 5 is a schematic illustration of a MU PPDU structure, in accordancewith some demonstrative embodiments.

FIG. 6 is a schematic illustration of a MU PPDU structure, in accordancewith some demonstrative embodiments.

FIG. 7 is a schematic flow-chart illustration of a method of multi-userwireless communication, in accordance with some demonstrativeembodiments.

FIG. 8 is a schematic illustration of a product of manufacture, inaccordance with some demonstrative embodiments.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are setforth in order to provide a thorough understanding of some embodiments.However, it will be understood by persons of ordinary skill in the artthat some embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components, unitsand/or circuits have not been described in detail so as not to obscurethe discussion.

Discussions herein utilizing terms such as, for example, “processing”,“computing”, “calculating”, “determining”, “establishing”, “analyzing”,“checking”, or the like, may refer to operation(s) and/or process(es) ofa computer, a computing platform, a computing system, or otherelectronic computing device, that manipulate and/or transform datarepresented as physical (e.g., electronic) quantities within thecomputer's registers and/or memories into other data similarlyrepresented as physical quantities within the computer's registersand/or memories or other information storage medium that may storeinstructions to perform operations and/or processes.

The terms “plurality” and “a plurality”, as used herein, include, forexample, “multiple” or “two or more”. For example, “a plurality ofitems” includes two or more items.

References to “one embodiment”, “an embodiment”, “demonstrativeembodiment”, “various embodiments” etc., indicate that the embodiment(s)so described may include a particular feature, structure, orcharacteristic, but not every embodiment necessarily includes theparticular feature, structure, or characteristic. Further, repeated useof the phrase “in one embodiment” does not necessarily refer to the sameembodiment, although it may.

As used herein, unless otherwise specified the use of the ordinaladjectives “first”, “second”, “third” etc., to describe a common object,merely indicate that different instances of like objects are beingreferred to, and are not intended to imply that the objects so describedmust be in a given sequence, either temporally, spatially, in ranking,or in any other manner.

Some embodiments may be used in conjunction with various devices andsystems, for example, a User Equipment (UE), a Mobile Device (MD), awireless station (STA), a Personal Computer (PC), a desktop computer, amobile computer, a laptop computer, a notebook computer, a tabletcomputer, an Internet of Things (IoT) device, a sensor device, a servercomputer, a handheld computer, a handheld device, a Personal DigitalAssistant (PDA) device, a handheld PDA device, an on-board device, anoff-board device, a hybrid device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a consumer device, a non-mobile ornon-portable device, a wireless communication station, a wirelesscommunication device, a wireless Access Point (AP), a wired or wirelessrouter, a wired or wireless modem, a video device, an audio device, anaudio-video (A/V) device, a wired or wireless network, a wireless areanetwork, a Wireless Video Area Network (WVAN), a Local Area Network(LAN), a Wireless LAN (WLAN), a Personal Area Network (PAN), a WirelessPAN (WPAN), and the like.

Some embodiments may be used in conjunction with devices and/or networksoperating in accordance with existing IEEE 802.11 standards (IEEE802.11-2012, IEEE Standard for Information technology—Telecommunicationsand information exchange between systems Local and metropolitan areanetworks—Specific requirements Part 11: Wireless LAN Medium AccessControl (MAC) and Physical Layer (PHY) Specifications, Mar. 29, 2012;IEEE802.11ac-2013 (“IEEE P802.11ac-2013, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 4: Enhancements for Very High Throughput forOperation in Bands below 6 GHz”, December, 2013); IEEE 802.11ad (“IEEEP802.11ad-2012, IEEE Standard for InformationTechnology—Telecommunications and Information Exchange BetweenSystems—Local and Metropolitan Area Networks—Specific Requirements—Part11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment 3: Enhancements for Very High Throughput in the60 GHz Band”, 28 Dec., 2012); IEEE-802.11REVmc (“IEEE802.11-REVmc™/D3.0, June 2014 draft standard for Informationtechnology—Telecommunications and information exchange between systemsLocal and metropolitan area networks Specific requirements; Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specification”); IEEE802.11-ay (P802.11ay Standard for InformationTechnology—Telecommunications and Information Exchange Between SystemsLocal and Metropolitan Area Networks—Specific Requirements Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)Specifications—Amendment: Enhanced Throughput for Operation inLicense-Exempt Bands Above 45 GHz)) and/or future versions and/orderivatives thereof, devices and/or networks operating in accordancewith existing Wireless-Gigabit-Alliance (WGA) specifications (WirelessGigabit Alliance, Inc WiGig MAC and PHY Specification Version 1.1, April2011, Final specification) and/or future versions and/or derivativesthereof, devices and/or networks operating in accordance with existingWireless Fidelity (WiFi) Alliance (WFA) Peer-to-Peer (P2P)specifications (including “WiFi Peer-to-Peer (P2P) technicalspecification, version 1.5, Aug. 4, 2014”) and/or future versions and/orderivatives thereof, devices and/or networks operating in accordancewith existing cellular specifications and/or protocols, e.g., 3rdGeneration Partnership Project (3GPP), 3GPP Long Term Evolution (LTE)and/or future versions and/or derivatives thereof, units and/or deviceswhich are part of the above networks, and the like.

Some embodiments may be used in conjunction with one way and/or two-wayradio communication systems, cellular radio-telephone communicationsystems, a mobile phone, a cellular telephone, a wireless telephone, aPersonal Communication Systems (PCS) device, a PDA device whichincorporates a wireless communication device, a mobile or portableGlobal Positioning System (GPS) device, a device which incorporates aGPS receiver or transceiver or chip, a device which incorporates an RFIDelement or chip, a Multiple Input Multiple Output (MIMO) transceiver ordevice, a Single Input Multiple Output (SIMO) transceiver or device, aMultiple Input Single Output (MISO) transceiver or device, a devicehaving one or more internal antennas and/or external antennas, DigitalVideo Broadcast (DVB) devices or systems, multi-standard radio devicesor systems, a wired or wireless handheld device, e.g., a Smartphone, aWireless Application Protocol (WAP) device, or the like.

Some embodiments may be used in conjunction with one or more types ofwireless communication signals and/or systems, for example, RadioFrequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM),Orthogonal FDM (OFDM), Orthogonal Frequency-Division Multiple Access(OFDMA), FDM Time-Division Multiplexing (TDM), Time-Division MultipleAccess (TDMA), Multi-User MIMO (MU-MIMO), Spatial Division MultipleAccess (SDMA), Extended TDMA (E-TDMA), General Packet Radio Service(GPRS), extended GPRS, Code-Division Multiple Access (CDMA), WidebandCDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA,Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth®,Global Positioning System (GPS), Wi-Fi, Wi-Max, ZigBee™, Ultra-Wideband(UWB), Global System for Mobile communication (GSM), 2G, 2.5G, 3G, 3.5G,4G, Fifth Generation (5G), or Sixth Generation (6G) mobile networks,3GPP, Long Term Evolution (LTE), LTE advanced, Enhanced Data rates forGSM Evolution (EDGE), or the like. Other embodiments may be used invarious other devices, systems and/or networks.

The term “wireless device”, as used herein, includes, for example, adevice capable of wireless communication, a communication device capableof wireless communication, a communication station capable of wirelesscommunication, a portable or non-portable device capable of wirelesscommunication, or the like. In some demonstrative embodiments, awireless device may be or may include a peripheral that is integratedwith a computer, or a peripheral that is attached to a computer. In somedemonstrative embodiments, the term “wireless device” may optionallyinclude a wireless service.

The term “communicating” as used herein with respect to a communicationsignal includes transmitting the communication signal and/or receivingthe communication signal. For example, a communication unit, which iscapable of communicating a communication signal, may include atransmitter to transmit the communication signal to at least one othercommunication unit, and/or a communication receiver to receive thecommunication signal from at least one other communication unit. Theverb communicating may be used to refer to the action of transmitting orthe action of receiving. In one example, the phrase “communicating asignal” may refer to the action of transmitting the signal by a firstdevice, and may not necessarily include the action of receiving thesignal by a second device. In another example, the phrase “communicatinga signal” may refer to the action of receiving the signal by a firstdevice, and may not necessarily include the action of transmitting thesignal by a second device.

Some demonstrative embodiments may be used in conjunction with a WLAN,e.g., a wireless fidelity (WiFi) network. Other embodiments may be usedin conjunction with any other suitable wireless communication network,for example, a wireless area network, a “piconet”, a WPAN, a WVAN andthe like.

Some demonstrative embodiments may be used in conjunction with awireless communication network communicating over a frequency band of 60GHz. However, other embodiments may be implemented utilizing any othersuitable wireless communication frequency bands, for example, anExtremely High Frequency (EHF) band (the millimeter wave (mmWave)frequency band), e.g., a frequency band within the frequency band ofbetween 20 Ghz and 300 GHZ, a frequency band above 45 GHZ, a frequencyband below 20 GHZ, e.g., a Sub 1 GHZ (S1G) band, a 2.4 GHz band, a 5 GHZband, a WLAN frequency band, a WPAN frequency band, a frequency bandaccording to the WGA specification, and the like.

The term “antenna”, as used herein, may include any suitableconfiguration, structure and/or arrangement of one or more antennaelements, components, units, assemblies and/or arrays. In someembodiments, the antenna may implement transmit and receivefunctionalities using separate transmit and receive antenna elements. Insome embodiments, the antenna may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements. The antenna may include, for example, a phased array antenna,a single element antenna, a set of switched beam antennas, and/or thelike.

The phrases “directional multi-gigabit (DMG)” and “directional band”(DBand), as used herein, may relate to a frequency band wherein theChannel starting frequency is above 45 GHz. In one example, DMGcommunications may involve one or more directional links to communicateat a rate of multiple gigabits per second, for example, at least 1Gigabit per second, e.g., 7 Gigabit per second, or any other rate.

Some demonstrative embodiments may be implemented by a DMG STA (alsoreferred to as a “mmWave STA (mSTA)”), which may include for example, aSTA having a radio transmitter, which is capable of operating on achannel that is within the DMG band. The DMG STA may perform otheradditional or alternative functionality. Other embodiments may beimplemented by any other apparatus, device and/or station.

Reference is made to FIG. 1, which schematically illustrates a system100, in accordance with some demonstrative embodiments.

As shown in FIG. 1, in some demonstrative embodiments, system 100 mayinclude one or more wireless communication devices. For example, system100 may include a wireless communication device 102, a wirelesscommunication device 140, a wireless communication device 115, and/orone more other devices.

In some demonstrative embodiments, devices 102, 115, and/or 140 mayinclude a mobile device or a non-mobile, e.g., a static, device.

For example, devices 102, 115, and/or 140 may include, for example, aUE, an MD, a STA, an AP, a PC, a desktop computer, a mobile computer, alaptop computer, an Ultrabook™ computer, a notebook computer, a tabletcomputer, a server computer, a handheld computer, a handheld device, anInternet of Things (IoT) device, a sensor device, a PDA device, ahandheld PDA device, an on-board device, an off-board device, a hybriddevice (e.g., combining cellular phone functionalities with PDA devicefunctionalities), a consumer device, a vehicular device, a non-vehiculardevice, a mobile or portable device, a non-mobile or non-portabledevice, a mobile phone, a cellular telephone, a PCS device, a PDA devicewhich incorporates a wireless communication device, a mobile or portableGPS device, a DVB device, a relatively small computing device, anon-desktop computer, a “Carry Small Live Large” (CSLL) device, an UltraMobile Device (UMD), an Ultra Mobile PC (UMPC), a Mobile Internet Device(MID), an “Origami” device or computing device, a device that supportsDynamically Composable Computing (DCC), a context-aware device, a videodevice, an audio device, an A/V device, a Set-Top-Box (STB), a Blu-raydisc (BD) player, a BD recorder, a Digital Video Disc (DVD) player, aHigh Definition (HD) DVD player, a DVD recorder, a HD DVD recorder, aPersonal Video Recorder (PVR), a broadcast HD receiver, a video source,an audio source, a video sink, an audio sink, a stereo tuner, abroadcast radio receiver, a flat panel display, a Personal Media Player(PMP), a digital video camera (DVC), a digital audio player, a speaker,an audio receiver, an audio amplifier, a gaming device, a data source, adata sink, a Digital Still camera (DSC), a media player, a Smartphone, atelevision, a music player, or the like.

In some demonstrative embodiments, device 102 may include, for example,one or more of a processor 191, an input unit 192, an output unit 193, amemory unit 194, and/or a storage unit 195; and/or devices 115 and/or140 may include, for example, one or more of a processor 181, an inputunit 182, an output unit 183, a memory unit 184, and/or a storage unit185. Devices 102, 115, and/or 140 may optionally include other suitablehardware components and/or software components. In some demonstrativeembodiments, some or all of the components of one or more of devices102, 115, and/or 140 may be enclosed in a common housing or packaging,and may be interconnected or operably associated using one or more wiredor wireless links. In other embodiments, components of one or more ofdevices 102, 115 and/or 140 may be distributed among multiple orseparate devices.

In some demonstrative embodiments, processor 191 and/or processor 181may include, for example, a Central Processing Unit (CPU), a DigitalSignal Processor (DSP), one or more processor cores, a single-coreprocessor, a dual-core processor, a multiple-core processor, amicroprocessor, a host processor, a controller, a plurality ofprocessors or controllers, a chip, a microchip, one or more circuits,circuitry, a logic unit, an Integrated Circuit (IC), anApplication-Specific IC (ASIC), or any other suitable multi-purpose orspecific processor or controller. Processor 191 executes instructions,for example, of an Operating System (OS) of device 102 and/or of one ormore suitable applications. Processor 181 executes instructions, forexample, of an Operating System (OS) of device 140 and/or of one or moresuitable applications.

In some demonstrative embodiments, input unit 192 and/or input unit 182may include, for example, a keyboard, a keypad, a mouse, a touch-screen,a touch-pad, a track-ball, a stylus, a microphone, or other suitablepointing device or input device. Output unit 193 and/or output unit 183may include, for example, a monitor, a screen, a touch-screen, a flatpanel display, a Light Emitting Diode (LED) display unit, a LiquidCrystal Display (LCD) display unit, a plasma display unit, one or moreaudio speakers or earphones, or other suitable output devices.

In some demonstrative embodiments, memory unit 194 and/or memory unit184 may include, for example, a Random Access Memory (RAM), a Read OnlyMemory (ROM), a Dynamic RAM (DRAM), a Synchronous DRAM (SD-RAM), a flashmemory, a volatile memory, a non-volatile memory, a cache memory, abuffer, a short term memory unit, a long term memory unit, or othersuitable memory units. Storage unit 195 and/or storage unit 185includes, for example, a hard disk drive, a floppy disk drive, a CompactDisk (CD) drive, a CD-ROM drive, a DVD drive, or other suitableremovable or non-removable storage units. Memory unit 194 and/or storageunit 195, for example, may store data processed by device 102. Memoryunit 184 and/or storage unit 185, for example, may store data processedby device 140.

In some demonstrative embodiments, wireless communication devices 102,115, and/or 140 may be capable of communicating content, data,information and/or signals via a wireless medium (WM) 103. In somedemonstrative embodiments, wireless medium 103 may include, for example,a radio channel, a cellular channel, an RF channel, a Wireless Fidelity(WiFi) channel, an IR channel, a Bluetooth (BT) channel, a GlobalNavigation Satellite System (GNSS) Channel, and the like.

In some demonstrative embodiments, WM 103 may include a directionalchannel. For example, WM 103 may include a millimeter-wave (mmWave)wireless communication channel.

In some demonstrative embodiments, WM 103 may include a DMG channel. Inother embodiments, WM 103 may include any other additional oralternative directional channel.

In other embodiments, WM 103 may include any other type of channel overany other frequency band.

In some demonstrative embodiments, devices 102, 115, and/or 140 mayperform the functionality of one or more wireless stations, e.g., asdescribed below.

In some demonstrative embodiments, devices 102, 115, and/or 140 mayperform the functionality of one or more DMG stations.

In other embodiments, devices 102, 115, and/or 140 may perform thefunctionality of any other wireless device and/or station, e.g., a WLANSTA, a WiFi STA, and the like.

In some demonstrative embodiments, devices 102, 115, and/or 140 mayinclude one or more radios including circuitry and/or logic to performwireless communication between devices 102, 115, 140 and/or one or moreother wireless communication devices. For example, device 102 mayinclude a radio 114, and/or devices 115 and/or 140 may include a radio144.

In some demonstrative embodiments, radios 114 and/or 144 may include oneor more wireless receivers (Rx) including circuitry and/or logic toreceive wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, radio 114 may include a receiver 116, and/or radio 144 mayinclude a receiver 146.

In some demonstrative embodiments, radios 114 and/or 144 may include oneor more wireless transmitters (Tx) including circuitry and/or logic tosend wireless communication signals, RF signals, frames, blocks,transmission streams, packets, messages, data items, and/or data. Forexample, radio 114 may include a transmitter 118, and/or radio 144 mayinclude a transmitter 148.

In some demonstrative embodiments, radios 114 and/or 144 may includecircuitry, logic, modulation elements, demodulation elements,amplifiers, analog to digital and digital to analog converters, filters,and/or the like. For example, radios 114 and/or 144 may include or maybe implemented as part of a wireless Network Interface Card (NIC), andthe like.

In some demonstrative embodiments, radios 114 and/or 144 may include, ormay be associated with, one or more antennas 107 and/or 147,respectively.

In one example, device 102 may include a single antenna 107. In otherexample, device 102 may include two or more antennas 107.

In one example, device 140 and/or device 115 may include a singleantenna 147. In another example, device 140 and/or device 115 mayinclude two or more antennas 147.

Antennas 107 and/or 147 may include any type of antennas suitable fortransmitting and/or receiving wireless communication signals, blocks,frames, transmission streams, packets, messages and/or data. Forexample, antennas 107 and/or 147 may include any suitable configuration,structure and/or arrangement of one or more antenna elements,components, units, assemblies and/or arrays. Antennas 107 and/or 147 mayinclude, for example, antennas suitable for directional communication,e.g., using beamforming techniques. For example, antennas 107 and/or 147may include a phased array antenna, a multiple element antenna, a set ofswitched beam antennas, and/or the like. In some embodiments, antennas107 and/or 147 may implement transmit and receive functionalities usingseparate transmit and receive antenna elements. In some embodiments,antennas 107 and/or 147 may implement transmit and receivefunctionalities using common and/or integrated transmit/receiveelements.

In some demonstrative embodiments, antennas 107 and/or 147 may include adirectional antenna, which may be steered to a plurality of beamdirections.

In some demonstrative embodiments, antennas 107 and/or 147 may include adirectional antenna, which may be steered to a plurality of beamdirections. For example, antenna 107 may be steered to a plurality ofbeam directions 135, and/or antenna 147 may be steered to a plurality ofbeam directions 145. For example, device 102 may transmit a directionaltransmission 139 to device 140, e.g., via a direction 133, and/or device140 may transmit a directional transmission 149 to device 102, e.g., viaa direction 143.

In some demonstrative embodiments, device 102 may include a controller124, and/or devices 140 and/or 115 may include a controller 154.Controllers 124 and/or 154 may be configured to perform one or morecommunications, may generate and/or communicate one or more messagesand/or transmissions, and/or may perform one or more functionalities,operations and/or procedures between devices 102, 115, and/or 140 and/orone or more other devices, e.g., as described below.

In some demonstrative embodiments, controllers 124 and/or 154 mayinclude circuitry and/or logic, e.g., one or more processors includingcircuitry and/or logic, memory circuitry and/or logic, Media-AccessControl (MAC) circuitry and/or logic, Physical Layer (PHY) circuitryand/or logic, and/or any other circuitry and/or logic, configured toperform the functionality of controllers 124 and/or 154, respectively.Additionally or alternatively, one or more functionalities ofcontrollers 124 and/or 154 may be implemented by logic, which may beexecuted by a machine and/or one or more processors, e.g., as describedbelow.

In one example, controller 124 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 102, and/or a wireless station,e.g., a wireless STA implemented by device 102, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In one example, controller 154 may include circuitry and/or logic, forexample, one or more processors including circuitry and/or logic, tocause a wireless device, e.g., device 140, and/or a wireless station,e.g., a wireless STA implemented by device 140, to perform one or moreoperations, communications and/or functionalities, e.g., as describedherein.

In some demonstrative embodiments, device 102 may include a messageprocessor 128 configured to generate, process and/or access one ormessages communicated by device 102.

In one example, message processor 128 may be configured to generate oneor more messages to be transmitted by device 102, and/or messageprocessor 128 may be configured to access and/or to process one or moremessages received by device 102, e.g., as described below. In oneexample, message processor 128 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 102; and/or message processor 128 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 102.

In some demonstrative embodiments, device 140 may include a messageprocessor 158 configured to generate, process and/or access one ormessages communicated by device 140.

In one example, message processor 158 may be configured to generate oneor more messages to be transmitted by device 140, and/or messageprocessor 158 may be configured to access and/or to process one or moremessages received by device 140, e.g., as described below. In oneexample, message processor 158 may be configured to process transmissionof one or more messages from a wireless station, e.g., a wireless STAimplemented by device 140; and/or message processor 158 may beconfigured to process reception of one or more messages by a wirelessstation, e.g., a wireless STA implemented by device 140.

In some demonstrative embodiments, message processors 128 and/or 158 mayinclude circuitry, e.g., processor circuitry, memory circuitry,Media-Access Control (MAC) circuitry, Physical Layer (PHY) circuitry,and/or any other circuitry, configured to perform the functionality ofmessage processors 128 and/or 158. Additionally or alternatively, one ormore functionalities of message processors 128 and/or 158 may beimplemented by logic, which may be executed by a machine and/or one ormore processors, e.g., as described below.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of radio 114, and/or atleast part of the functionality of message processor 158 may beimplemented as part of radio 144.

In some demonstrative embodiments, at least part of the functionality ofmessage processor 128 may be implemented as part of controller 124,and/or at least part of the functionality of message processor 158 maybe implemented as part of controller 154.

In other embodiments, the functionality of message processor 128 may beimplemented as part of any other element of device 102, and/or thefunctionality of message processor 158 may be implemented as part of anyother element of device 140.

In some demonstrative embodiments, at least part of the functionality ofcontroller 124 and/or message processor 128 may be implemented by anintegrated circuit, for example, a chip, e.g., a System in Chip (SoC).In one example, the chip or SoC may be configured to perform one or morefunctionalities of radio 114. For example, the chip or SoC may includeone or more elements of controller 124, one or more elements of messageprocessor 128, and/or one or more elements of radio 114. In one example,controller 124, message processor 128, and radio 114 may be implementedas part of the chip or SoC.

In other embodiments, controller 124, message processor 128 and/or radio114 may be implemented by one or more additional or alternative elementsof device 102.

In some demonstrative embodiments, at least part of the functionality ofcontroller 154 and/or message processor 158 may be implemented by anintegrated circuit, for example, a chip, e.g., a SoC. In one example,the chip or SoC may be configured to perform one or more functionalitiesof radio 144. For example, the chip or SoC may include one or moreelements of controller 154, one or more elements of message processor158, and/or one or more elements of radio 144. In one example,controller 154, message processor 158, and radio 144 may be implementedas part of the chip or SoC.

In other embodiments, controller 154, message processor 158 and/or radio144 may be implemented by one or more additional or alternative elementsof device 140.

In some demonstrative embodiments, devices 102, 115, and/or 140 may beconfigured to perform the functionality of an access point (AP), e.g., aDMG AP, and/or a personal basic service set (PBSS) control point (PCP),e.g., a DMG PCP, for example, an AP/PCP STA, e.g., a DMG AP/PCP STA.

In some demonstrative embodiments, devices 102, 115, and/or 140 may beconfigured to perform the functionality of a non-AP STA, e.g., a DMGnon-AP STA, and/or a non-PCP STA, e.g., a DMG non-PCP STA, for example,a non-AP/PCP STA, e.g., a DMG non-AP/PCP STA.

In one example, a station (STA) may include a logical entity that is asingly addressable instance of a medium access control (MAC) andphysical layer (PHY) interface to the wireless medium (WM). The STA mayperform any other additional or alternative functionality.

In one example, an AP may include an entity that contains a station(STA), e.g., one STA, and provides access to distribution services, viathe wireless medium (WM) for associated STAs. The AP may perform anyother additional or alternative functionality.

In one example, a personal basic service set (PBSS) control point (PCP)may include an entity that contains a STA, e.g., one station (STA), andcoordinates access to the wireless medium (WM) by STAs that are membersof a PBSS. The PCP may perform any other additional or alternativefunctionality.

In one example, a PBSS may include a directional multi-gigabit (DMG)basic service set (BSS) that includes, for example, one PBSS controlpoint (PCP). For example, access to a distribution system (DS) may notbe present, but, for example, an intra-PBSS forwarding service mayoptionally be present.

In one example, a PCP/AP STA may include a station (STA) that is atleast one of a PCP or an AP. The PCP/AP STA may perform any otheradditional or alternative functionality.

In one example, a non-AP STA may include a STA that is not containedwithin an AP. The non-AP STA may perform any other additional oralternative functionality.

In one example, a non-PCP STA may include a STA that is not a PCP. Thenon-PCP STA may perform any other additional or alternativefunctionality.

In one example, a non PCP/AP STA may include a STA that is not a PCP andthat is not an AP. The non-PCP/AP STA may perform any other additionalor alternative functionality.

Some specifications may be configured to support communications over asingle channel bandwidth (BW) of a wireless communication band, forexample, a DMG band or any other band. For example, the IEEE 802.11adSpecification defines a 60 GHz system with a single channel bandwidth(BW) of 2.16 GHz, which is to be used by all Stations (STAs) for bothtransmission and reception.

In some demonstrative embodiments, devices 102, 115, and/or 140 may beconfigured to implement one or more mechanisms, which may, for example,enable to extend a single-channel BW scheme, e.g., a scheme inaccordance with the IEEE 802.11ad Specification or any other scheme, forhigher data rates and/or increased capabilities, e.g., as describedbelow.

In some demonstrative embodiments, devices 102, 115, and/or 140 may beconfigured to implement one or more channel bonding mechanisms, whichmay, for example, support communication over bonded channels.

In some demonstrative embodiments, the channel bonding may include, forexample, a mechanism and/or an operation whereby two or more channelscan be combined, e.g., for a higher bandwidth of packet transmission,for example, to enable achieving higher data rates, for example,compared to transmissions over a non-bonded channel, e.g., a singlechannel.

In some demonstrative embodiments, devices 102, 115 and/or 140 may beconfigured to implement one or more channel bonding mechanisms, whichmay for example, support an increased channel bandwidth, for example, achannel BW of 4.32 GHz, a channel BW of 6.48 GHz, and/or any otheradditional or alternative channel BW.

Some specifications, e.g., the IEEE 802.11ad-2012 Specification, may beconfigured to support a Single User (SU) system, in which a Station(STA) cannot transmit frames to more than a single STA at a time. Suchspecifications may not be able, for example, to support transmissionfrom a STA to multiple STAs, e.g., simultaneously.

In some demonstrative embodiments, devices 102, 140, and/or 115 may beconfigured to support simultaneous transmission from a STA, e.g., a STAimplemented by device 102, to multiple STAs, e.g., including a STAimplemented by device 140 and/or a STA implemented by device 115, forexample, using a multi-user MIMO (MU-MIMO) scheme, e.g., a downlink (DL)MU-MIMO, and/or any other MU scheme.

In some demonstrative embodiments, devices 102, 115, and/or 140 may beconfigured to implement one or more Multi-User (MU) mechanisms. Forexample, devices 102, 115, and/or 140 may be configured to implement oneor more MU mechanisms, which may be configured to enable MUcommunication.

In some demonstrative embodiments, devices 102, 140 and/or 115 may beconfigured to implement one or more MU mechanisms, which may beconfigured to enable MU communication of Downlink (DL) frames using aMultiple-Input-Multiple-Output (MIMO) scheme, for example, between adevice, e.g., device 102, and a plurality of devices, e.g., includingdevices 140, 115 and/or one or more other devices, e.g., as describedbelow.

In some demonstrative embodiments, devices 102, 115 and/or 140 may beconfigured to implement any other additional or alternative MUmechanism, e.g., to communicate MU transmissions, and/or any other MIMOmechanism, e.g., to communicate MIMO transmissions.

In some demonstrative embodiments, devices 102, 115, and/or 140 may beconfigured to communicate over a Next Generation 60 GHz (NG60) network,an Extended DMG (EDMG) network, and/or any other network and/or anyother frequency band. For example, devices 102, 115, and/or 140 may beconfigured to communicate DL MU-MIMO transmissions and/or use channelbonding, for example, for communicating over the NG60 and/or EDMGnetworks.

FIG. 2 is a schematic illustration of a Multi-User (MU) scheme includingtwo groups of Stations (STAs), in accordance with some demonstrativeembodiments.

For example, as shown in FIG. 2, a STA 202 may be configured tocommunicate with a first group, denoted group 1, which may include fourSTAs, e.g., a STA A 204, a STA B 206, a STA C 208, and a STA D 210;and/or a second group, denoted group 2, which may include three STAs,e.g., a STA E 220, a STA F 222, and a STAG 224.

In one example, device 102 (FIG. 1) may perform the functionality of STA202, device 115 (FIG. 1) may perform the functionality of one of STAs204, 206, 208, 210, 220, 222, and/or 224, and/or device 140 (FIG. 1) mayperform the functionality of another one of STAs 204, 206, 208, 210,220, 222, and/or 224.

Referring back to FIG. 1, in some demonstrative embodiments, devices102, 140 and/or 115 may be configured according to a communicationscheme, which may include changes to an IEEE 802.11 Specification, e.g.,the IEEE 802.11ad-2012 Specification, for example, at least in aPhysical layer (PHY) and/or a Media Access Control (MAC) layer, forexample, to support MU capabilities. For example, a PHY header, aPhysical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU)format and/or MU MIMO signaling may be configured to enable the MUcommunications, e.g., as described below.

In some demonstrative embodiments, devices 102, 140 and/or 115 may beconfigured according to a communication scheme, which include a Physicallayer (PHY) and/or a Media Access Control (MAC) layer, for example, tosupport MU capabilities. For example, the communication scheme mayinclude a PHY header, a Physical Layer Convergence Protocol (PLCP)Protocol Data Unit (PPDU) format and/or MU MIMO signaling, which may beconfigured to enable the MU communications, e.g., as described below.

In some demonstrative embodiments, the communication scheme may be basedon, or may include, for example, changes to an IEEE 802.11Specification, e.g., the IEEE 802.11ad-2012 Specification. In otherembodiments, the communication scheme may be based on, or may includechanges to any other Specification or protocol. In other embodiments,the communication scheme may include a new and/or dedicated scheme.

In some demonstrative embodiments, devices 102, 140 and/or 115 may beconfigured to utilize a PPDU structure, which may be configured, forexample, at least for MU directional communication, for example, over aDMG band, e.g., as described below.

In some demonstrative embodiments, a PPDU structure may be configured inaccordance with unique requirements for beamforming in a directionalband, for example, in a DMG band, e.g., in a 60 Gigahertz (GHz) band.

In some demonstrative embodiments, devices 102, 115 and/or 140 may beconfigured to use a PPDU structure, for example, in accordance with anIEEE 802.11ad Specification, which may include optional Automatic GainControl (AGC) and/or Training (TRN) fields, e.g., at the end of thePPDU.

Reference is made to FIG. 3, which schematically illustrates a PhysicalLayer Convergence Protocol (PLCP) Protocol Data Unit (PPDU) structure300, in accordance with some demonstrative embodiments.

In some demonstrative embodiments, PPDU structure 300 may be configured,for example, to support communication according to a MU MIMOconfiguration, for example, over a directional band, e.g., as describedbelow.

In some demonstrative embodiments, PPDU structure 300 may be configuredto support use of AGC and/or TRN fields, for example, for both transmitand receive beamforming, e.g., in the 60 GHz band. In one example, someframes, e.g., frames that do not require beamforming, may not carry theAGC and/or TRN fields, e.g., as described below.

In some demonstrative embodiments, the directional PPDU structure ofFIG. 3 may be configured, for example, at least to support communicationaccording to a MU MIMO configuration, e.g., as described below.

In some demonstrative embodiments, device 102 (FIG. 1), device 115 (FIG.1), and/or device 140 (FIG. 1) may be configured to process transmissionand/or reception of the PPDU structure 300. For example, device 102(FIG. 1) may be configured to generate and transmit a frame, e.g., a MUPPDU, having the PPDU structure 300, and/or devices 115 and/or 140(FIG. 1) may be configured to process reception of a frame, e.g., a MUPPDU, having the PPDU structure 300, e.g., as described below.

In some demonstrative embodiments, as shown in FIG. 3, PPDU 300 mayinclude a Short Training Field (STF) 302, a channel estimation (CE)field 304, a header portion 306, a data portion 314, an Automatic GainControl (AGC) field 316, and/or a Training (TRN) field 318.

In some demonstrative embodiments, header portion 306 may include a PHYheader portion.

In some demonstrative embodiments, header portion 306 may include a PLCPheader portion, e.g., of a PPDU including the fields of frame structure300.

In some demonstrative embodiments, a header structure of header portion306 may be configured to support NG60 and/or EDMG communication, and/orany other type and/or form of communication, e.g., as described below.

In some demonstrative embodiments, as shown in FIG. 3, header portion306 may include a legacy header (L-Header) 308.

In some demonstrative embodiments, legacy header 308 may include aheader, which may have a structure in accordance with a current, legacyand/or conventional header.

In some demonstrative embodiments, legacy header 308 may have astructure, which may be processed, decoded and/or demodulated by one ormore legacy, existing and/or conventional, e.g., devices which maycurrently be in the market.

In some demonstrative embodiments, legacy header 308 may have astructure, which may be in accordance with a PHY header structure of anIEEE 802.11 Specification, for example, the IEEE 802.11ad-2012Specification, and/or any other Specification, protocol or Standard.

In some demonstrative embodiments, legacy header 308 may include aSingle Carrier (SC) header. In other embodiments, legacy header 308 mayinclude an OFDM header, and/or any other header.

In some demonstrative embodiments, header portion 306 may be configuredto include one or more new information headers, which may be included aspart of a PLCP header of PPDU 300, e.g., as described below

In some demonstrative embodiments, header portion 306 may be configuredto include a non-legacy information header 305, which may be included aspart of a PLCP header of PPDU 300, e.g., as described below

In some demonstrative embodiments, non-legacy header 305 may include afirst non-legacy header 310, denoted “NG60 Header A” or “EDMG Header A”,e.g., as described below.

In some demonstrative embodiments, non-legacy header 305 may include asecond non-legacy header 312, denoted “NG60 Header B” or “EDMG HeaderB”.

In other embodiments, non-legacy headers 310 and 312 may be combinedinto a single header 305 and/or may be divided into more than twoheaders.

In some demonstrative embodiments, non-legacy header 312 may follow thenon-legacy header 310.

In some demonstrative embodiments, non-legacy header 312 may immediatelyfollow the non-legacy header 310.

In some demonstrative embodiments, the non-legacy header 312 may notimmediately follow the non-legacy header 310.

For example, non-legacy header 305 may include one or more fields, forexample, training fields, between non-legacy header 310 and non-legacyheader 312.

For example, non-legacy header 305 may include one or more fields, forexample, one or more STF fields and/or one or more CE fields betweennon-legacy header 310 and non-legacy header 312, e.g., as describedbelow with reference to FIG. 5.

In some demonstrative embodiments, non-legacy headers 310 and 312 maydiffer from each other, for example, at least with respect to where inthe PPDU structure 300 non-legacy headers 310 and/or 312 may beincluded; and/or with respect to the contents, functionality, intent,and/or purpose of non-legacy headers 310 and/or 312.

In some demonstrative embodiments, as shown in FIG. 3, non-legacy header310 may be included, for example, immediately after the legacy header308.

In some demonstrative embodiments, non-legacy header 310 may beconfigured, for example, to include information pertaining to, and/or tobe used by, both single user (SU) transmissions of a SU PPDU, and MUtransmissions of a MU PPDU, e.g., as described below.

In some demonstrative embodiments, non-legacy header 312 may beconfigured, for example, to include information pertaining to, and/or tobe used by, MU transmissions, e.g., as described below. In one example,non-legacy header 312 may optionally be excluded from structure 300, forexample, in a SU transmission.

In some demonstrative embodiments, non-legacy header 312 may beincluded, for example, on a per SS basis, e.g., as described below.

In some demonstrative embodiments, non-legacy header 310 may include,for example, information of a number of channels to be bonded, e.g., totransmit at least data portion 314; a length of the PPDU, e.g., a lengthof at least data portion 314 and/or one or more elements of frame 300; aCyclic Prefix (CP) interval; a number of spatial streams, e.g., totransmit at least data portion 314 to one or more users; and/or anyother additional or alternative information.

In some demonstrative embodiments, non-legacy header 312 may include,for example, MU-MIMO parameters, for example, information relating toSpatial Streams (SS), beamforming variables, training sequences, e.g.,to be applied to at least data portion 314, and/or any other additionalor alternative information.

In some demonstrative embodiments, at least some of the information ofnon-legacy header 312 may be included in non-legacy header 310, forexample, in addition to or instead of including the information innon-legacy header 312.

In some demonstrative embodiments, data portion 314 may include aplurality of Spatial Streams (SSs) of MAC Protocol Data Units (MPDUs),e.g., Aggregate MPDUs (A-MPDUs), to a plurality of users, e.g., asdescribed below.

For example, controller 124 (FIG. 1) may be configured to cause awireless station, e.g., a wireless station implemented by device 102(FIG. 1), to generate and process transmission of an MU PPDU, e.g., inaccordance with the PPDU structure 300, to a plurality of users, e.g., aplurality of stations implemented by devices 140 (FIG. 1), 115 (FIG. 1)and/or one or more other devices. For example, the MU PPDU may include,e.g., in data portion 314, a plurality of spatial streams of MPDUs tothe plurality of users, e.g., as described below.

In some demonstrative embodiments, header field 305 may include lengthinformation 370 to indicate one or more of lengths of one or morerespective MPDUs of the plurality of MPDUs in data portion 314, e.g., asdescribed below.

In one example, data portion 314 may include three SSs, e.g., to threeusers. According to this example, length information 370 may include afirst length value to indicate a length of an MPDU of a first SS in dataportion 314, a second length value to indicate a length of an MPDU of asecond SS in data portion 314, and/or a third length value to indicate alength of an MPDU of a third SS in data portion 314, e.g., as describedbelow.

Referring back to FIG. 1, in some demonstrative embodiments, devices102, 115 and/or 140 may be configured to communicate MU transmissions,for example, such that, for example, transmission to each user in a MUtransmission may end at substantially the same time, e.g., as describedbelow.

In some demonstrative embodiments, configuring the transmission to eachuser to end at the same time may enable, for example, to keep thewireless medium busy, and/or prevent other STAs that are not in the MUgroup, which is to receive the MU transmission, from transmitting.

In some demonstrative embodiments, an MU PPDU format using MAC paddingmay not be suitable and/or efficient, e.g., for MU directionalcommunication, e.g., over a DMG band, as discussed below.

FIG. 4 is a schematic illustration of a MU PPDU structure 400 usingMedia Access Control (MAC) padding, for example, for 5 GHz systems orother systems, e.g., in accordance with an IEEE 802.11ac Specification,for example, with respect to a group including three users.

As shown in FIG. 4, MAC padding 404 may be inserted after an AggregateMAC Protocol Data Unit (A-MPDU) 402, for example, to ensure that thetransmission to each user in the PPDU ends at the same time 406. Asshown in FIG. 4, after the MAC padding 404, a very short PHY padding405, e.g., a PHY padding of not more than 7 bits, can be added to thepacket.

In some demonstrative embodiments, the MU PPDU structure 400 includingthe MAC padding 404 may not be suitable for use with respect to a PPDUstructure including the AGC and/or TRN fields, e.g., PPDU structure 300(FIG. 3) including AGC field 316 (FIG. 3) and/or TRN field 318 (FIG. 3).

For example, using the MAC padding 404 in the PPDU structure 400 maysuffice, for example, since there is no PHY field (Tail is not presentwhen LDPC is used) after the end of the Physical Layer Service Data Unit(PSDU). For example, as soon as a receiving STA receives the first MACpadding with an EOF field set to 1, the receiving STA may stop receivingand potentially turn off its receiver completely.

In contrast to the PPDU structure 400, a directional PPDU structure,e.g., PPDU structure 300 (FIG. 3), may include the AGC field 3176 (FIG.3) and/or the TRN field 318 (FIG. 3) following a PSDU including datafield 314 (FIG. 3).

In some demonstrative embodiments, the AGC field 316 (FIG. 3) and/or TRNfield 318 (FIG. 3) may be used, for example, as part of a beamformingprocedure, which may performed, for example, in order to enable adirectional transmission of PPDU structure 300 (FIG. 3). Accordingly,MAC padding, e.g., according to the PPDU structure of FIG. 4, may lead areceiver STA to consume more power, for example, since the receiver STAwould have to stay awake waiting for the AGC and TRN fields after theA-MPDU ends.

Referring back to FIG. 1, in some demonstrative embodiments, accordingto one approach (“Approach 1”), devices 102, 115 and/or 140 may beconfigured to communicate a MU transmission using the PPDU structure 300(FIG. 3), for example, by adding PHY padding to the MU PPDU structure,e.g., as describe below.

In some demonstrative embodiments, the PHY padding may be configured,for example, to allow the construction of the MU PPDU, for example, suchthat all transmissions to each user addressed by the MU PPDU end at thesame time, e.g., as described below.

In other embodiments, transmission of AGC field 316 (FIG. 3) and/or TRNfield 318 may be avoided, e.g., prohibited, for example, when performinga MU MIMO transmission, e.g., as described below.

In some demonstrative embodiments, according to another approach(“Approach 2”), a device, e.g., device 102, may be prohibited to performtransmission of, or may be configured to avoid transmission of, the AGCfield 316 (FIG. 3) and/or the TRN field 318 (FIG. 3), for example, whena MU PPDU is transmitted.

According to these embodiments, MAC padding may be used, for example,instead of PHY padding. In one example, a specification, e.g., an IEEE802.11ay Specification or any other specification, may be configured toprohibit transmission of the AGC field 316 (FIG. 3) and/or the TRN field318 (FIG. 3), for example, when a MU PPDU is transmitted.

In some demonstrative embodiments, for example, if transmission of theAGC field 316 (FIG. 1) and/or TRN field 318 (FIG. 1) in the MU PPDU isto be allowed, e.g., according to Approach 1, a transmitter of a MU MIMOPPDU, e.g., device 102 (FIG. 1), may be configured to construct the MUPPDU, for example, such that all transmissions, e.g., to each individualSTA in the MU MIMO group, may end at the same time, e.g., as describedbelow.

In some demonstrative embodiments, for example, according to theApproach 1, a two pronged approach may be used, for example, to avoidthe potential problems described above with respect to MAC padding,e.g., as described below.

In some demonstrative embodiments, the MU PPDU structure may beconfigured such that transmissions to each individual STA in the MU MIMOgroup may end at the same time, for example, by inclusion of a field inheader portion 306 (FIG. 3), e.g., in header 312 (FIG. 3), for example,length information field 370 (FIG. 3) to indicate a length of the A-MPDUfor a user, e.g., in octets.

In some demonstrative embodiments, the MU PPDU structure may beconfigured such that transmissions, e.g., to each individual STA in theMU MIMO group, may end at the same time, for example, by inclusion of aPHY padding following one or more MPDUs in the PHY PPDU structure 300(FIG. 3), e.g., to align the end of the transmission to each user, asdescribed below.

In some demonstrative embodiments, controller 124 may be configured tocause a wireless station, e.g., a STA implemented by device 102, togenerate a MU PPDU, e.g., according to PPDU structure 30 (FIG. 3),including a header field, e.g., header field 305 (FIG. 3), and aplurality of MPDUs to a respective plurality of users, e.g., in dataportion 314 (FIG. 3).

In some demonstrative embodiments, an MPDU of the plurality of MPDUs mayinclude an A-MPDU, for example, including a plurality of A-MPDUsubframes, e.g., as described below.

In some demonstrative embodiments, the header field may include anindication, e.g., in length field 370 (FIG. 3), of one or more lengthsof respective ones of one or more of the plurality of MPDUs, e.g., asdescribed above.

In some demonstrative embodiments, the header field may include anindication, e.g., in length field 370 (FIG. 3), of a plurality oflengths of respective ones of the plurality of MPDUs, e.g., as describedabove.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to generate the MU PPDU such that one or moreMPDUs of the plurality of MPDUs are followed by one or more respectivePHY padding portions extending to an end of a longest MPDU of theplurality of MPDUs, e.g., as described below.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to process transmission of the MU PPDU to theplurality of users over a wireless communication band, for example, adirectional band, e.g., a DMG band, or any other band.

In some demonstrative embodiments, each MPDU of the plurality of MPDUs,except for the longest MPDU, may followed by a PHY padding portionextending to the end of the longest MPDU. According to theseembodiments, all PSDUs, e.g., including the MPDUs and the PHY paddingportions, may be extended to end at an end of the longest MPDU, e.g., asdescribed below.

In some demonstrative embodiments, at least one first MPDU may have afirst MPDU length, and at least one second MPDU may have a second MPDUlength, e.g., different from the first MPDU length. According to theseembodiments, the first MPDU may be followed by a first PHY paddingportion having a first padding length, and the second MPDU followed by asecond padding portion having a second padding length. For example, asum of the first MPDU length and the first padding length may be equalto a sum of the second MPDU length and the second padding length.

In some demonstrative embodiments, the one or more PHY padding portionsmay include at least one dummy PHY data block, e.g., having a structuresimilar to data field 314 (FIG. 3).

In some demonstrative embodiments, the one or more PHY padding portionsmay include at least one dummy Training field, e.g., having a structuresimilar to TRN field 318 (FIG. 3).

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to generate the MU PPDU including at leastone PHY field, for example, following a PSDU, e.g., as described below.

In some demonstrative embodiments, at least one PHY padding portion ofthe one or more PHY padding portions may be followed by at least one PHYfield.

In some demonstrative embodiments, the at least one PHY field mayinclude, for example, at lest one AGC field and/or at least one TRNfield, e.g., at least one AGC field 314 (FIG. 3), followed by at leastTRN field 316 (FIG. 3).

In some demonstrative embodiments, each of the PHY padding portions maybe followed by the at least one PHY field, e.g., the same PHY field.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to generate the MU PPDU including the atleast one PHY field, e.g., the same PHY field following the PHY paddingportions, for example, after the longest MPDU.

In some demonstrative embodiments, controller 124 may be configured tocause the wireless station to generate the MU PPDU including anindication of the length of the longest MPDU.

In some demonstrative embodiments, a legacy header of the MU PPDU, e.g.,legacy header 308 (FIG. 3), may include a length field. For example,controller 124 may cause the wireless station to set the length field ofthe legacy header 308 (FIG. 3) to indicate the length of at least thelongest MPDU.

In some demonstrative embodiments, controller 154 may be configured tocause a wireless station, e.g., a wireless station implemented by device140, to process reception of an MU PPDU (“the received MU PPDU”)including a plurality of MPDUs to a plurality of users. For example, thereceived MU PPDU may include the MU PPDU transmitted by device 102.

In some demonstrative embodiments, controller 154 may be configured tocause the wireless station to process reception of an MPDU addressed tothe wireless station, for example, based on a length of the MPDUindicated by the header field, e.g., based on a length indication inlength field 370 (FIG. 3) corresponding to the MPDU addressed to thewireless station.

Reference is made to FIG. 5, which schematically illustrates a MU PPDUstructure 500, in accordance with some demonstrative embodiments.

In some demonstrative embodiments, device 102 (FIG. 1), device 115 (FIG.1), and/or device 140 (FIG. 1) may be configured to process transmissionand/or reception of the MU PPDU structure 500. For example, device 102(FIG. 1) may be configured to generate and transmit a frame having theMU PPDU structure 500, for example, to a plurality of users, e.g., N>1users, for example, of an MU group, e.g., including devices 115 and/or140 (FIG. 1). For example, device 102 (FIG. 1) may transmit MU PPDU 500over a directional band, e.g., over a DMG band. For example, devices 115and/or 140 (FIG. 1) may be configured to process reception the MU PPDUstructure 500, e.g., as described below. For example, as shown in FIG.5, MU PPDU structure 500 may be transmitted to N=3 users.

In some demonstrative embodiments, MU PPDU 500 may include a legacy STF(L-STF) 502, a legacy CE (L-CE) field 504, and a header field 506, e.g.,as described below. For example, L-STF 502 may include STF 302 (FIG. 3),L-CE 504 may include CE field 304 (FIG. 3), and/or header field 506 mayinclude header 306 (FIG. 3).

In some demonstrative embodiments, header field 506 may include a legacyheader (L-Header) 508, a first non-legacy header 510, and a secondnon-legacy header 512. For example, legacy header 508 may include legacyheader 308 (FIG. 3), non-legacy header 510 may include non-legacy header310 (FIG. 3), and/or non-legacy header 512 may include non-legacy header312 (FIG. 3).

In some demonstrative embodiments, header field 506 may also include anon-legacy STF 553, e.g., an EDMG-STF or NG60-STF; and/or a non-legacyCE field 555, e.g., an EDMG-CE or NG60 CE.

In some demonstrative embodiments, MU PPDU 500 may include a PHY ServiceData Unit (PSDU) including a plurality of Spatial Streams (SSs) to theplurality of users, e.g., as described below.

For example, as shown in FIG. 5, MU PPDU 500 may include an SS 580 to afirst user (“user 1”), an SS 582 to a second user (“user 2”), and/or anSS 584 to a third user (“user 3”). In other embodiments, MU PPDU 500 mayinclude any other number of SS to any other number of users.

In some demonstrative embodiments, SS 580 may include, for example, anA-MPDU 534, e.g., an EDMG A-MPDU or an NG60 A-MPDU; SS 582 may include,for example, an A-MPDU 544, e.g., an EDMG A-MPDU or an NG60 A-MPDU;and/or SS 584 may include, for example, an A-MPDU 554, e.g., an EDMGA-MPDU or an NG60 A-MPDU.

In some demonstrative embodiments, as shown in FIG. 5, A-MPDU 534,A-MPDU 544, and/or A-MPDU 554 may include a plurality of A-MPDUsubframes, e.g., including A-MPDU subframes 516, 518, and/or 520.

In some demonstrative embodiments, as shown in FIG. 5, A-MPDU 534,A-MPDU 544, and/or A-MPDU 554 may optionally include a MAC paddingportion 521.

In some demonstrative embodiments, MU PPDU 500 may be generated and/ortransmitted by a STA implemented by device 102 (FIG. 1), a STAimplemented by device 140 (FIG. 1) may perform the functionality of auser of users 1, 2, and/or 3, and/or STA implemented by device 115(FIG. 1) may perform the functionality of another one of users 1, 2and/or 3.

In some demonstrative embodiments, as shown in FIG. 5, the same legacyheader 508 may be provided to the plurality of users of the MUtransmission.

In some demonstrative embodiments, non-legacy header 510 may includeinformation of a number of channels to be bonded, e.g., to communicateSSs 580, 582, and/or 584; a length of the MU PPDU 500; a Cyclic Prefix(CP) interval; a number of spatial streams, e.g., to transmit at leastSSs 580, 582, and/or 584; and/or any other additional or alternativeinformation.

In some demonstrative embodiments, field 553, field 555, and/ornon-legacy header 512 may include information, for example, on a per SSbasis, e.g., as described below.

In some demonstrative embodiments, as shown in FIG. 5, non-legacy STF553, non-legacy CE field 555 and/or non-legacy header field 512 mayinclude information corresponding to the plurality of spatial streams.For example, non-legacy STF 553 may indicate first STF informationcorresponding to SS 580, second STF information corresponding to SS 582,and/or third STF information corresponding to SS 584; non-legacy CEfield 555 may indicate first CE information corresponding to SS 580,second CE information corresponding to SS 582, and/or third CEinformation corresponding to SS 584; and/or non-legacy header 512 mayindicate first parameters corresponding to SS 580, second parameterscorresponding to SS 582, and/or third parameters corresponding to SS584, e.g., as described below.

In some demonstrative embodiments, non-legacy header 512 may include,for example, MU-MIMO parameters, for example, spatial streams,beamforming variables, training sequences, and the like.

For example, as shown in FIG. 5, non-legacy header 512 may indicatefirst MU-MIMO parameters corresponding to SS 580, second MU-MIMOparameters corresponding to SS 582, and/or third MU-MIMO parameterscorresponding to SS 584.

In some demonstrative embodiments, a MU PPDU, e.g., MU PPDU 500, may beconfigured not to include one or more PHY fields, e.g., one or more AGCand/or TRN fields, following the PSDU, e.g., as shown in FIG. 5.

In other embodiments, a MU PPDU may be configured to include one or morePHY fields, e.g., one or more AGC and/or TRN fields, following the PSDU,e.g., as described below with reference to FIG. 6.

In some demonstrative embodiments, MU PPDU structure 500 may include afield (“indication field”), which may be configured to indicate to areceiver of the MU PPDU 500 an end time of an A-MPDU addressed to thereceiver, e.g., as described below.

In some demonstrative embodiments, header field 505 may include theindication field, e.g., as described below.

In some demonstrative embodiments, non-legacy header 512 may include theindication field, e.g., as described below. For example, the indicationfield may be configured to enable a receiver, e.g., each receiver,addressed by the MU PPDU 500, e.g., device 115 and/or device 140 (FIG.1), to know the end of the A-MPDU to be received by the receiver.

In some demonstrative embodiments, non-legacy heard field 512 mayinclude at least one length field, which may include a first lengthindication or field 503 to indicate a length of an A-MPDU, e.g., A-MPDU534, of the SS 580; a second length indication or field 513 to indicatea length of an A-MPDU, e.g., A-MPDU 544, of the SS 582; and/or a thirdlength indication or field 523 to indicate a length of an A-MPDU, e.g.,A-MPDU 554, of the SS 584.

In some demonstrative embodiments, A-MPDU transmissions to differentusers may have different lengths. For example, as shown in FIG. 5,A-MPDU 534 may have a first length, A-MPDU 554 may have a second length,e.g., longer than the first length, and A-MPDU 544 may have a thirdlength, e.g., longer than the second length.

In some demonstrative embodiments, a transmitter of MU PPDU 500, e.g.,device 102 (FIG. 1) may be configured to pad the PSDU, for example, suchthat all PPDUs in the MU PPDU end at the same time, e.g., as describedbelow.

In some demonstrative embodiments, controller 124 (FIG. 1) may beconfigured to cause the wireless station implemented by device 102(FIG. 1) to add PHY padding portions following A-MPDUs of MU PPDU 500,e.g., to extend the PSDU to an end of a longest MPDU of MU PPDU 500,e.g., to an end of A-MPDU 544.

For example, as shown in FIG. 5, controller 124 (FIG. 1) may beconfigured to cause the wireless station implemented by device 102(FIG. 1) to add a PHY padding portion 540 following A-MPDU 534, and/or aPHY padding portion 542 following A-MPDU 554.

For example, as shown in FIG. 5, PHY padding portion 540 and PHY paddingportion 542 may both extend until an end of A-MPDU 544.

In some demonstrative embodiments, as shown in FIG. 5, the amount of PHYpadding may be variable, for example, if the length of each A-MPDU toeach user is different.

In some demonstrative embodiments, the length of PHY padding portion 540may be determined, for example, based on the length A-MPDU 534 and thelength of longest MPDU in MU PPDU 500, e.g., the length of A-MPDU 544;and/or the length of PHY padding portion 542 may be determined, forexample, based on the length A-MPDU 554 and the length of longest MPDUin MU PPDU 500, e.g., the length of A-MPDU 544.

For example, the sum of the length of A-MPDU 534 and the length of PHYpadding portion 540 may be equal to the length of A-MPDU 544; and/or thesum of the length of A-MPDU 554 and the length of PHY padding portion542 may be equal to the length of A-MPDU 544.

In some demonstrative embodiments, the transmitter of MU PPDU 500, e.g.,device 102 (FIG. 1) may be configured to include PHY padding portions540 and/or 542 at the end of the PPDU. The PHY padding portions 540and/or 542 may be inserted, for example, directly by a PHY of thetransmitter of MU PPDU 500, e.g., without involvement from the MAC.

In some demonstrative embodiments, the transmitter of the MU PPDU, e.g.,device 102 (FIG. 1), may include enough PHY padding in MU PPDU 500, forexample, until the end of the PPDU, e.g., as may be indicated in theL-Header field 508.

In some demonstrative embodiments, the PHY of the transmitter of MU PPDU500 may be configured to ensure that the transmission to each user endsat the same time, for example, while using a reduced amount, e.g.,minimal amount, of padding across users. In one example, this may be animplementation requirement for the PHY.

In some demonstrative embodiments, the transmitter of MU PPDU 500, e.g.,device 102 (FIG. 1), may be configured to include any suitable contentin PHY padding portions 540 and/or 542. In one example, PHY paddingportions may include one or more PHY data blocks, e.g., dummy PHY datablocks. In another example, PHY padding portions may include one or moreTRN fields, e.g., dummy TRN fields. The PHY may have, for example, thecapability to transmit both types of content, and therefore bothimplementations may be simple.

In some demonstrative embodiments, from the perspective of thetransmitter of MU PPDU 500, e.g., device 102 (FIG. 1), whether AGC andTRN fields are included or not in the frame, the transmitter may beallowed to pad the PSDU, e.g., such that all PPDUs in the MU PPDU end atthe same time.

In some demonstrative embodiments, a receiver of the MU PPDU of FIG. 5(“the receiver STA”) may be able to use the indication fieldcorresponding to a SS addressed to the receiver STA to determine, e.g.,exactly, when the A-MPDU, which is to be received by the receiver STA,is to end, and when one or more next PHY fields, e.g., if present, AGCand/or TRN fields, may start.

In some demonstrative embodiments, controller 154 (FIG. 1) may beconfigured to process a length field, e.g., length field 513,corresponding to an SS, e.g., SS 580, addressed to the wireless stationimplemented by device 140 (FIG. 1). Controller 154 may be configured todetermine, based on the length field, when an A-MPDU, e.g., A-MPDU 534,which is to be received by the wireless station, is to end.

In some demonstrative embodiments, e.g., as shown in FIG. 5, the MU PPDUmay not include AGC and/or TRN fields, for example, after the A-MPDUends. According to these embodiments, the receiver STA may know if theAGC and/or TRN fields are not included, e.g., based on the legacyheader. In such case, the receiver STA may stop reception, e.g., andeven turn off its receiver, for example, without any negativeimplications, e.g., since all elements of the frame have already beenreceived.

For example, as shown in FIG. 5, a STA addressed by SS 580, e.g., a STAimplemented by device 140 (FIG. 1), may determine an end time 591 ofA-MPDU 534, e.g., based on length field 503, and may stop reception, oreven power down of power off a receiver of the STA addressed by SS 580,e.g., until at least an end of MU PPDU 500.

For example, as shown in FIG. 5, a STA addressed by SS 584, e.g., a STAimplemented by device 115 (FIG. 1), may determine an end time 593 ofA-MPDU 554, e.g., based on length field 523, and may stop reception, oreven power down of power off a receiver of the STA addressed by SS 584,e.g., until at least an end of MU PPDU 500.

For example, as shown in FIG. 5, a STA addressed by SS 582 may determinean end time 595 of A-MPDU 544, e.g., based on length field 513.

In some demonstrative embodiments, from the receiver perspective, e.g.,device 115 and/or 140 (FIG. 1), the content of the PHY padding portions540 and/or 542 may be irrelevant, for example, since the receiver maydetermine the end of the PPDU, and may be able to stop processingreception of the MU PPDU, e.g., as shown in FIG. 5.

Reference is made to FIG. 6, which schematically illustrates a MU PPDUstructure 600, in accordance with some demonstrative embodiments.

In some demonstrative embodiments, device 102 (FIG. 1), device 115 (FIG.1), and/or device 140 (FIG. 1) may be configured to process transmissionand/or reception of the MU PPDU structure 600. For example, device 102(FIG. 1) may be configured to generate and transmit a frame having theMU PPDU structure 600, for example, to a plurality of users, e.g., N>1users, for example, of an MU group, e.g., including devices 115 and/or140 (FIG. 1). For example, device 102 (FIG. 1) may transmit MU PPDU 600over a directional band, e.g., over a DMG band. For example, devices 115and/or 140 (FIG. 1) may be configured to process reception the MU PPDUstructure 600, e.g., as described below. For example, as shown in FIG.6, MU PPDU structure 600 may be transmitted to N=3 users.

In some demonstrative embodiments, MU PPDU 600 may include a PSDUincluding a plurality of SSs to the plurality of users, e.g., asdescribed below.

For example, as shown in FIG. 6, MU PPDU 600 may include an SS 680 to afirst user (“user 1”), an SS 682 to a second user (“user 2”), and/or anSS 684 to a third user (“user 3”). In other embodiments, MU PPDU 600 mayinclude any other number of SS to any other number of users.

In some demonstrative embodiments, SS 680 may include, for example, anA-MPDU 634, e.g., an EDMG A-MPDU or an NG60 A-MPDU; SS 682 may include,for example, an A-MPDU 644, e.g., an EDMG A-MPDU or an NG60 A-MPDU;and/or SS 684 may include, for example, an A-MPDU 654, e.g., an EDMGA-MPDU or an NG60 A-MPDU.

In some demonstrative embodiments, MU PPDU 600 may include a PHY paddingportion 640 following A-MPDU 634, and/or a PHY padding portion 642following A-MPDU 654. For example, PHY padding portions 640 and/or 642may extended to an end of A-MPDU 644, e.g., as described above.

In some demonstrative embodiments, MU MIMO PPDU 600 may be configured toinclude AGC and/or TRN fields, e.g., following the longest A-MPDU,and/or the PHY padding portions.

For example, as shown in FIG. 6, SS 680 may include at least one AGCfield 687 and/or at least one TRN field 688, e.g., following paddingportion 640; SS 682 may include the AGC field 687 and/or a TRN field688, e.g., following A-MPDU 644; and/or SS 684 may include the AGC field687 and/or TRN field 688, e.g., following padding portion 642.

In some demonstrative embodiments, the same AGC field 687 and/or TRNfield 688 may be included in each of SSs 680, 682, and 684.

In other embodiments, any other configuration and/or arrangement of AGCand/or TRN fields may be used with respect to SS 680, SS 682 and/or SS684.

In some demonstrative embodiments, as shown in FIG. 6, MU PPDU 600 mayinclude the AGC field 687 and/or the TRN field 688, for example, afterthe longest A-MPDU ends, e.g., at the end of A-MPDU 644.

In some demonstrative embodiments, the presence of the AGC field 687and/or the TRN field 688 may be signaled in a legacy header field, e.g.,a legacy header 608, for example, in compliance with an IEEE 802.11adSpecification.

In some demonstrative embodiments, the presence of the AGC field 687and/or the TRN field 688 may be signaled in an EDMG Header-A.

In some demonstrative embodiments, a receiver of the MU PPDU 600 maystart receiving the AGC and/or TRN fields, e.g., immediately after theend of the longest A-MPDU.

For example, controller 154 (FIG. 1) may be configured to cause thewireless station implemented by device 140 (FIG. 1) to process receptionof MU PPDU 600 including a SS, e.g., SS 680, addressed to the wirelessstation. Controller 154 (FIG. 1) may be configured to determine thelength of A-MPDU 634, for example, based on a length field 603, forexample, in a non-legacy header 612 of MU PPDU 600, e.g., as describedabove. Controller 154 (FIG. 1) may be configured to determine a time toreceive AGC field 687 and/or TRN field 688, for example, based on thelength field in legacy header 608.

In some demonstrative embodiments, according to Approach 2, transmissionof the AGC and TRN fields may be prohibited in MU PPDUs.

In some demonstrative embodiments, prohibiting the transmission of AGCand/or TRN fields in MU PPDUs may, for example, avoid changes to thePPDU structure. For example, the MAC may be responsible for all padding,e.g., without requiring PHY changes. Therefore, absent any PPDUstructure changes at the PHY, it may be advantageous to prohibit AGCand/or TRN field transmission when performing a MU MIMO PPDUtransmission.

Reference is made to FIG. 7, which schematically illustrates a method ofMU wireless communication, in accordance with some demonstrativeembodiments. For example, one or more of the operations of the method ofFIG. 7 may be performed by one or more elements of a system, e.g.,system 100 (FIG. 1), for example, one or more wireless devices, e.g.,device 102 (FIG. 1), device 115 (FIG. 1), and/or device 140 (FIG. 1), acontroller, e.g., controller 124 (FIG. 1) and/or controller 154 (FIG.1), a radio, e.g., radio 114 (FIG. 1) and/or radio 144 (FIG. 1), and/ora message processor, e.g., message processor 128 (FIG. 1) and/or messageprocessor 158 (FIG. 1).

As indicated at block 702, the method may include generating a PPDUincluding a header field and a plurality of MPDUs to a respectiveplurality of users, the header field including an indication of aplurality of lengths of respective ones of the plurality of MPDUs, oneor more MPDUs of the plurality of MPDUs being followed by one or morerespective PHY padding portions extending to an end of a longest MPDU ofthe plurality of MPDUs. For example, controller 124 (FIG. 1) may causemessage processor 128 (FIG. 1) to generate MU PPDU 500 (FIG. 5)including header field 512 (FIG. 5), which may include length fields503, 513, and/or 523 (FIG. 5), to indicate respective lengths of A-MPDUs534, 544 and/or 544 (FIG. 5), e.g., as described above. For example,controller 124 (FIG. 1) may cause message processor 128 (FIG. 1) toinclude in MU PPDU 500 (FIG. 5) the PHY padding portion 540 (FIG. 5),e.g., following A-MPDU 534 (FIG. 5), and/or the PHY padding portion 542(FIG. 5), e.g., following A-MPDU 544 (FIG. 5), as described above.

As indicated at block 704, the method may include processingtransmission of the MU PPDU to the plurality of users over a wirelesscommunication band. For example, controller 124 (FIG. 1) may causemessage processor 128 (FIG. 1) and/or radio 114 (FIG. 1) to processtransmission of PPDU 500 (FIG. 5) to the plurality of users, e.g.,including devices 115 and/or 140 (FIG. 1), via a wireless communicationband, for example, a DMG band, e.g., as described above.

As indicated at bock 706, the method may include processing reception ofthe MU PPDU at a wireless station. For example, controller 154 (FIG. 1)may cause message processor 158 (FIG. 1) and/or radio 144 (FIG. 1) toprocess reception of MU PPDU 500 (FIG. 5), e.g., as described above.

As indicated at block 708, the method may include processing receptionof an MPDU addressed to the wireless station, based at least on a lengthof the MPDU indicated by the header field. For example, controller 154(FIG. 1) may cause message processor 158 (FIG. 1) and/or radio 144(FIG. 1) to process reception of a SS addressed to the STA implementedby device 140 (FIG. 1), e.g., SS 580, 582, or 584 (FIG. 5), for example,based at least on a length of the MPDU indicated by the header field 512(FIG. 5), e.g., as described above.

Reference is made to FIG. 8, which schematically illustrates a productof manufacture 800, in accordance with some demonstrative embodiments.Product 800 may include a non-transitory machine-readable storage medium802 to store logic 804, which may be used, for example, to perform atleast part of the functionality of devices 102, 115, and/or 140 (FIG.1), transmitters 118 and/or 148 (FIG. 1), receivers 116 and/or 146 (FIG.1), controllers 124 and/or 154 (FIG. 1), and/or message processors 128(FIG. 1) and/or 158 (FIG. 1), and/or to perform one or more operationsand/or functionalities, for example, one or more operations of themethod of FIG. 7. The phrase “non-transitory machine-readable medium” isdirected to include all computer-readable media, with the sole exceptionbeing a transitory propagating signal.

In some demonstrative embodiments, product 800 and/or machine-readablestorage medium 802 may include one or more types of computer-readablestorage media capable of storing data, including volatile memory,non-volatile memory, removable or non-removable memory, erasable ornon-erasable memory, writeable or re-writeable memory, and the like. Forexample, machine-readable storage medium 802 may include, RAM, DRAM,Double-Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM,programmable ROM (PROM), erasable programmable ROM (EPROM), electricallyerasable programmable ROM (EEPROM), Compact Disk ROM (CD-ROM), CompactDisk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), flash memory(e.g., NOR or NAND flash memory), content addressable memory (CAM),polymer memory, phase-change memory, ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppydisk, a hard drive, an optical disk, a magnetic disk, a card, a magneticcard, an optical card, a tape, a cassette, and the like. Thecomputer-readable storage media may include any suitable media involvedwith downloading or transferring a computer program from a remotecomputer to a requesting computer carried by data signals embodied in acarrier wave or other propagation medium through a communication link,e.g., a modem, radio or network connection.

In some demonstrative embodiments, logic 804 may include instructions,data, and/or code, which, if executed by a machine, may cause themachine to perform a method, process and/or operations as describedherein. The machine may include, for example, any suitable processingplatform, computing platform, computing device, processing device,computing system, processing system, computer, processor, or the like,and may be implemented using any suitable combination of hardware,software, firmware, and the like.

In some demonstrative embodiments, logic 804 may include, or may beimplemented as, software, a software module, an application, a program,a subroutine, instructions, an instruction set, computing code, words,values, symbols, and the like. The instructions may include any suitabletype of code, such as source code, compiled code, interpreted code,executable code, static code, dynamic code, and the like. Theinstructions may be implemented according to a predefined computerlanguage, manner or syntax, for instructing a processor to perform acertain function. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Matlab,Pascal, Visual BASIC, assembly language, machine code, and the like.

EXAMPLES

The following examples pertain to further embodiments.

Example 1 includes an apparatus comprising circuitry configured to causea wireless station to generate a Multi-User (MU) Physical LayerConvergence Protocol (PLCP) Protocol Data Unit (PPDU) comprising aheader field and a plurality of Media Access Control (MAC) Protocol DataUnits (MPDUs) to a respective plurality of users, the header fieldcomprising an indication of a plurality of lengths of respective ones ofthe plurality of MPDUs, one or more MPDUs of the plurality of MPDUsbeing followed by one or more respective PHY padding portions extendingto an end of a longest MPDU of the plurality of MPDUs; and processtransmission of the MU PPDU to the plurality of users over a wirelesscommunication band.

Example 2 includes the subject matter of Example 1, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 3 includes the subject matter of Example 1 or 2, and optionally,wherein at least one PHY padding portion of the one or more PHY paddingportions is followed by at least one PHY field.

Example 4 includes the subject matter of Example 3, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 5 includes the subject matter of Example 3 or 4, and optionally,wherein each of the PHY padding portions is followed by the at least onePHY field.

Example 6 includes the subject matter of any one of Examples 3-5, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 7 includes the subject matter of any one of Examples 1-6, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 8 includes the subject matter of any one of Examples 1-7, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 9 includes the subject matter of Example 8, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 10 includes the subject matter of any one of Examples 1-9, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 11 includes the subject matter of any one of Examples 1-10, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 12 includes the subject matter of any one of Examples 1-11, andoptionally, wherein an MPDU of the plurality of MPDUs comprises anAggregate MPDU (A-MPDU) comprising a plurality of A-MPDU subframes.

Example 13 includes the subject matter of any one of Examples 1-12, andoptionally, wherein the wireless communication band is a DirectionalMulti-Gigabit (DMG) band.

Example 14 includes the subject matter of any one of Examples 1-13, andoptionally, wherein the wireless station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 15 includes the subject matter of any one of Examples 1-14, andoptionally, comprising a transmitter to transmit the MU PPDU.

Example 16 includes the subject matter of any one of Examples 1-15, andoptionally, comprising one or more directional antennas, a memory, and aprocessor.

Example 17 includes an apparatus comprising circuitry configured tocause a wireless station to process reception of a Multi-User (MU)Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU)comprising a header field and a plurality of Media Access Control (MAC)Protocol Data Units (MPDUs) to a respective plurality of users, theheader field comprising an indication of a plurality of lengths ofrespective ones of the plurality of MPDUs, one or more MPDUs of theplurality of MPDUs being followed by one or more respective PHY paddingportions extending to an end of a longest MPDU of the plurality ofMPDUs; and process reception of an MPDU addressed to the wirelessstation, based on a length of the MPDU indicated by the header field.

Example 18 includes the subject matter of Example 17, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 19 includes the subject matter of Example 17 or 18, andoptionally, configured to cause the wireless station to process at leastone PHY field after a PHY padding portion following the MPDU.

Example 20 includes the subject matter of Example 19, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 21 includes the subject matter of Example 19 or 20, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 22 includes the subject matter of any one of Examples 19-21, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 23 includes the subject matter of any one of Examples 17-22, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 24 includes the subject matter of any one of Examples 17-23, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 25 includes the subject matter of Example 24, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 26 includes the subject matter of any one of Examples 17-25, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 27 includes the subject matter of any one of Examples 17-26, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 28 includes the subject matter of any one of Examples 17-27, andoptionally, wherein the MPDU addressed to the wireless station comprisesan Aggregate MPDU (A-MPDU) comprising a plurality of A-MPDU subframes.

Example 29 includes the subject matter of any one of Examples 17-28, andoptionally, configured to cause the wireless station to processreception of the MU PPDU over a Directional Multi-Gigabit (DMG) band.

Example 30 includes the subject matter of any one of Examples 17-29, andoptionally, wherein the wireless station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 31 includes the subject matter of any one of Examples 17-30, andoptionally, comprising a receiver to receive the MU PPDU.

Example 32 includes the subject matter of any one of Examples 17-31, andoptionally, comprising one or more directional antennas, a memory, and aprocessor.

Example 33 includes a method to be performed at a wireless station, themethod comprising generating a Multi-User (MU) Physical LayerConvergence Protocol (PLCP) Protocol Data Unit (PPDU) comprising aheader field and a plurality of Media Access Control (MAC) Protocol DataUnits (MPDUs) to a respective plurality of users, the header fieldcomprising an indication of a plurality of lengths of respective ones ofthe plurality of MPDUs, one or more MPDUs of the plurality of MPDUsbeing followed by one or more respective PHY padding portions extendingto an end of a longest MPDU of the plurality of MPDUs; and transmittingthe MU PPDU to the plurality of users over a wireless communicationband.

Example 34 includes the subject matter of Example 33, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 35 includes the subject matter of Example 33 or 34, andoptionally, wherein at least one PHY padding portion of the one or morePHY padding portions is followed by at least one PHY field.

Example 36 includes the subject matter of Example 35, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 37 includes the subject matter of Example 35 or 36, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 38 includes the subject matter of any one of Examples 35-37, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 39 includes the subject matter of any one of Examples 33-38, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 40 includes the subject matter of any one of Examples 33-39, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 41 includes the subject matter of Example 40, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 42 includes the subject matter of any one of Examples 33-41, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 43 includes the subject matter of any one of Examples 33-42, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 44 includes the subject matter of any one of Examples 33-43, andoptionally, wherein an MPDU of the plurality of MPDUs comprises anAggregate MPDU (A-MPDU) comprising a plurality of A-MPDU subframes.

Example 45 includes the subject matter of any one of Examples 33-44, andoptionally, wherein the wireless communication band is a DirectionalMulti-Gigabit (DMG) band.

Example 46 includes the subject matter of any one of Examples 33-45, andoptionally, wherein the wireless station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 47 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a wireless station, the operationscomprising generating a Multi-User (MU) Physical Layer ConvergenceProtocol (PLCP) Protocol Data Unit (PPDU) comprising a header field anda plurality of Media Access Control (MAC) Protocol Data Units (MPDUs) toa respective plurality of users, the header field comprising anindication of a plurality of lengths of respective ones of the pluralityof MPDUs, one or more MPDUs of the plurality of MPDUs being followed byone or more respective PHY padding portions extending to an end of alongest MPDU of the plurality of MPDUs; and transmitting the MU PPDU tothe plurality of users over a wireless communication band.

Example 48 includes the subject matter of Example 47, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 49 includes the subject matter of Example 47 or 48, andoptionally, wherein at least one PHY padding portion of the one or morePHY padding portions is followed by at least one PHY field.

Example 50 includes the subject matter of Example 49, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 51 includes the subject matter of Example 49 or 50, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 52 includes the subject matter of any one of Examples 49-51, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 53 includes the subject matter of any one of Examples 49-52, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 54 includes the subject matter of any one of Examples 49-53, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 55 includes the subject matter of Example 54, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 56 includes the subject matter of any one of Examples 49-55, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 57 includes the subject matter of any one of Examples 49-56, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 58 includes the subject matter of any one of Examples 49-57, andoptionally, wherein an MPDU of the plurality of MPDUs comprises anAggregate MPDU (A-MPDU) comprising a plurality of A-MPDU subframes.

Example 59 includes the subject matter of any one of Examples 49-58, andoptionally, wherein the wireless communication band is a DirectionalMulti-Gigabit (DMG) band.

Example 60 includes the subject matter of any one of Examples 49-59, andoptionally, wherein the wireless station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 61 includes an apparatus of wireless communication by a wirelessstation, the apparatus comprising means for generating a Multi-User (MU)Physical Layer Convergence Protocol (PLCP) Protocol Data Unit (PPDU)comprising a header field and a plurality of Media Access Control (MAC)Protocol Data Units (MPDUs) to a respective plurality of users, theheader field comprising an indication of a plurality of lengths ofrespective ones of the plurality of MPDUs, one or more MPDUs of theplurality of MPDUs being followed by one or more respective PHY paddingportions extending to an end of a longest MPDU of the plurality ofMPDUs; and means for processing transmission of the MU PPDU to theplurality of users over a wireless communication band.

Example 62 includes the subject matter of Example 61, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 63 includes the subject matter of Example 61 or 62, andoptionally, wherein at least one PHY padding portion of the one or morePHY padding portions is followed by at least one PHY field.

Example 64 includes the subject matter of Example 63, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 65 includes the subject matter of Example 63 or 64, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 66 includes the subject matter of any one of Examples 63-65, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 67 includes the subject matter of any one of Examples 61-66, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 68 includes the subject matter of any one of Examples 61-67, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 69 includes the subject matter of Example 68, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 70 includes the subject matter of any one of Examples 61-69, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 71 includes the subject matter of any one of Examples 61-70, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 72 includes the subject matter of any one of Examples 61-71, andoptionally, wherein an MPDU of the plurality of MPDUs comprises anAggregate MPDU (A-MPDU) comprising a plurality of A-MPDU subframes.

Example 73 includes the subject matter of any one of Examples 61-72, andoptionally, wherein the wireless communication band is a DirectionalMulti-Gigabit (DMG) band.

Example 74 includes the subject matter of any one of Examples 61-73, andoptionally, wherein the wireless station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 75 includes a method to be performed at a wireless station, themethod comprising processing a received Multi-User (MU) Physical LayerConvergence Protocol (PLCP) Protocol Data Unit (PPDU) comprising aheader field and a plurality of Media Access Control (MAC) Protocol DataUnits (MPDUs), the header field comprising an indication of a pluralityof lengths of respective ones of the plurality of MPDUs, one or moreMPDUs of the plurality of MPDUs being followed by one or more respectivePHY padding portions extending to an end of a longest MPDU of theplurality of MPDUs; and processing a received MPDU addressed to thewireless station, based on a length of the MPDU indicated by the headerfield.

Example 76 includes the subject matter of Example 75, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 77 includes the subject matter of Example 75 or 76, andoptionally, comprising processing at least one PHY field after a PHYpadding portion following the MPDU.

Example 78 includes the subject matter of Example 77, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 79 includes the subject matter of Example 77 or 78, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 80 includes the subject matter of any one of Examples 77-79, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 81 includes the subject matter of any one of Examples 75-80, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 82 includes the subject matter of any one of Examples 75-81, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 83 includes the subject matter of Example 82, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 84 includes the subject matter of any one of Examples 75-83, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 85 includes the subject matter of any one of Examples 75-84, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 86 includes the subject matter of any one of Examples 75-85, andoptionally, wherein the MPDU addressed to the wireless station comprisesan Aggregate MPDU (A-MPDU) comprising a plurality of A-MPDU subframes.

Example 87 includes the subject matter of any one of Examples 75-86, andoptionally, comprising processing reception of the MU PPDU over aDirectional Multi-Gigabit (DMG) band.

Example 88 includes the subject matter of any one of Examples 75-87, andoptionally, wherein the wireless station is a Directional Multi-Gigabit(DMG) Station (STA).

Example 89 includes a product comprising one or more tangiblecomputer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone computer processor, enable the at least one computer processor toimplement one or more operations at a wireless station, the operationscomprising processing a received Multi-User (MU) Physical LayerConvergence Protocol (PLCP) Protocol Data Unit (PPDU) comprising aheader field and a plurality of Media Access Control (MAC) Protocol DataUnits (MPDUs), the header field comprising an indication of a pluralityof lengths of respective ones of the plurality of MPDUs, one or moreMPDUs of the plurality of MPDUs being followed by one or more respectivePHY padding portions extending to an end of a longest MPDU of theplurality of MPDUs; and processing a received MPDU addressed to thewireless station, based on a length of the MPDU indicated by the headerfield.

Example 90 includes the subject matter of Example 89, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 91 includes the subject matter of Example 89 or 90, andoptionally, wherein the operations comprise processing at least one PHYfield after a PHY padding portion following the MPDU.

Example 92 includes the subject matter of Example 91, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 93 includes the subject matter of Example 91 or 92, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 94 includes the subject matter of any one of Examples 91-93, andoptionally, wherein the at least one PHY field comprises at least onefield selected from the group consisting of an Automatic Gain Control(AGC) field, and a Training (TRN) field.

Example 95 includes the subject matter of any one of Examples 89-94, andoptionally, wherein the plurality of MPDUs comprise at least one firstMPDU having a first MPDU length, and at least one second MPDU having asecond MPDU length, different from the first MPDU length, the first MPDUfollowed by a first PHY padding portion having a first padding length,and the second MPDU followed by a second padding portion having a secondpadding length, a sum of the first MPDU length and the first paddinglength being equal to a sum of the second MPDU length and the secondpadding length.

Example 96 includes the subject matter of any one of Examples 89-95, andoptionally, wherein the MU PPDU comprises a legacy header field followedby at least one non-legacy header field, the non-legacy header fieldcomprising the indication of the plurality of lengths.

Example 97 includes the subject matter of Example 96, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 98 includes the subject matter of any one of Examples 89-97, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 99 includes the subject matter of any one of Examples 89-98, andoptionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 100 includes the subject matter of any one of Examples 89-99,and optionally, wherein the MPDU addressed to the wireless stationcomprises an Aggregate MPDU (A-MPDU) comprising a plurality of A-MPDUsubframes.

Example 101 includes the subject matter of any one of Examples 89-100,and optionally, wherein the operations comprise processing reception ofthe MU PPDU over a Directional Multi-Gigabit (DMG) band.

Example 102 includes the subject matter of any one of Examples 89-101,and optionally, wherein the wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Example 103 includes an apparatus of wireless communication by awireless station, the apparatus comprising means for processingreception of a Multi-User (MU) Physical Layer Convergence Protocol(PLCP) Protocol Data Unit (PPDU) comprising a header field and aplurality of Media Access Control (MAC) Protocol Data Units (MPDUs) to arespective plurality of users, the header field comprising an indicationof a plurality of lengths of respective ones of the plurality of MPDUs,one or more MPDUs of the plurality of MPDUs being followed by one ormore respective PHY padding portions extending to an end of a longestMPDU of the plurality of MPDUs; and means for processing reception of anMPDU addressed to the wireless station, based on a length of the MPDUindicated by the header field.

Example 104 includes the subject matter of Example 103, and optionally,wherein each MPDU of the plurality of MPDUs, except for the longestMPDU, is followed by a PHY padding portion extending to the end of thelongest MPDU.

Example 105 includes the subject matter of Example 103 or 104, andoptionally, comprising means for processing at least one PHY field aftera PHY padding portion following the MPDU.

Example 106 includes the subject matter of Example 105, and optionally,wherein the longest MPDU is followed by the at least one PHY field.

Example 107 includes the subject matter of Example 105 or 106, andoptionally, wherein each of the PHY padding portions is followed by theat least one PHY field.

Example 108 includes the subject matter of any one of Examples 105-107,and optionally, wherein the at least one PHY field comprises at leastone field selected from the group consisting of an Automatic GainControl (AGC) field, and a Training (TRN) field.

Example 109 includes the subject matter of any one of Examples 103-108,and optionally, wherein the plurality of MPDUs comprise at least onefirst MPDU having a first MPDU length, and at least one second MPDUhaving a second MPDU length, different from the first MPDU length, thefirst MPDU followed by a first PHY padding portion having a firstpadding length, and the second MPDU followed by a second padding portionhaving a second padding length, a sum of the first MPDU length and thefirst padding length being equal to a sum of the second MPDU length andthe second padding length.

Example 110 includes the subject matter of any one of Examples 103-109,and optionally, wherein the MU PPDU comprises a legacy header fieldfollowed by at least one non-legacy header field, the non-legacy headerfield comprising the indication of the plurality of lengths.

Example 111 includes the subject matter of Example 110, and optionally,wherein the legacy header comprises a length field to indicate a lengthof at least the longest MPDU.

Example 112 includes the subject matter of any one of Examples 103-111,and optionally, wherein the one or more PHY padding portions comprise atleast one dummy PHY data block.

Example 113 includes the subject matter of any one of Examples 103-112,and optionally, wherein the one or more PHY padding portions comprise atleast one dummy Training field.

Example 114 includes the subject matter of any one of Examples 103-113,and optionally, wherein the MPDU addressed to the wireless stationcomprises an Aggregate MPDU (A-MPDU) comprising a plurality of A-MPDUsubframes.

Example 115 includes the subject matter of any one of Examples 103-114,and optionally, comprising means for processing reception of the MU PPDUover a Directional Multi-Gigabit (DMG) band.

Example 116 includes the subject matter of any one of Examples 103-115,and optionally, wherein the wireless station is a DirectionalMulti-Gigabit (DMG) Station (STA).

Functions, operations, components and/or features described herein withreference to one or more embodiments, may be combined with, or may beutilized in combination with, one or more other functions, operations,components and/or features described herein with reference to one ormore other embodiments, or vice versa.

While certain features have been illustrated and described herein, manymodifications, substitutions, changes, and equivalents may occur tothose skilled in the art. It is, therefore, to be understood that theappended claims are intended to cover all such modifications and changesas fall within the true spirit of the disclosure.

1. (canceled)
 2. An apparatus comprising logic and circuitry configuredto cause a wireless communication station (STA) to: generate aMulti-User (MU) Physical Layer (PHY) Protocol Data Unit (PPDU)comprising a first header (L-header) field decodable by DirectionalMulti-Gigabit (DMG) stations, a second header (Header A) field after theL-header field, a third header (Header B) field after the Header Afield, and a data field after the Header B field, the data fieldcomprising a plurality of data units to a respective plurality of users,a data unit of the plurality of data units is padded with one or morePHY padding blocks to align said plurality of data units in time; andtransmit said MU PPDU to said plurality of users over a channelbandwidth in a frequency band above 45 Gigahertz (GHz).
 3. The apparatusof claim 2 configured to cause the STA to determine the one or more PHYpadding blocks based on a longest data unit of the plurality of dataunits.
 4. The apparatus of claim 2 configured to cause the STA todetermine the one or more PHY padding blocks for the data unit based ona value relating to a length of the data unit and a value relating to alength of a longest data unit of the plurality of data units.
 5. Theapparatus of claim 2 configured to cause the STA to determine the one ormore PHY padding blocks to extend the data unit to an end of a longestdata unit of the plurality of data units.
 6. The apparatus of claim 2configured to cause the STA to pad with the one or more PHY paddingblocks each data unit of the plurality of data units, which is shorterthan a longest data unit of the plurality of data units.
 7. Theapparatus of claim 2, wherein the plurality of data units comprises aplurality of Aggregate Medium Access Control (MAC) Protocol Data Units(A-MPDUs).
 8. The apparatus of claim 2, wherein the channel bandwidthcomprises one or more 2.16 GHz channels.
 9. The apparatus of claim 8,wherein the Header A field comprises an indication of the one or more2.16 GHz channels.
 10. The apparatus of claim 8, wherein the channelbandwidth comprises a channel bandwidth of 4.32 GHz or 6.48 GHz.
 11. Theapparatus of claim 2, wherein the MU PPDU comprises a Training (TRN)field after the data field.
 12. The apparatus of claim 2, wherein theHeader B field comprises a length field to indicate a length of the dataunit for the user.
 13. The apparatus of claim 2, wherein the MU PPDUcomprises an Extended Directional Multi-Gigabit (EDMG) MU PPDU, theHeader A field comprises an EDMG Header A field, and the Header B fieldcomprises an EDMG Header B field.
 14. The apparatus of claim 2comprising a Medium Access Control (MAC), and a Physical Layer (PHY).15. The apparatus of claim 2 comprising a radio.
 16. The apparatus ofclaim 2 comprising one or more antennas.
 17. A product comprising one ormore tangible computer-readable non-transitory storage media comprisingcomputer-executable instructions operable to, when executed by at leastone processor, enable the at least one processor to cause a wirelesscommunication station (STA) to: generate a Multi-User (MU) PhysicalLayer (PHY) Protocol Data Unit (PPDU) comprising a first header(L-header) field decodable by Directional Multi-Gigabit (DMG) stations,a second header (Header A) field after the L-header field, a thirdheader (Header B) field after the Header A field, and a data field afterthe Header B field, the data field comprising a plurality of data unitsto a respective plurality of users, a data unit of the plurality of dataunits is padded with one or more PHY padding blocks to align saidplurality of data units in time; and transmit said MU PPDU to saidplurality of users over a channel bandwidth in a frequency band above 45Gigahertz (GHz).
 18. The product of claim 17, wherein the instructions,when executed, cause the STA to determine the one or more PHY paddingblocks based on a longest data unit of the plurality of data units. 19.The product of claim 17, wherein the instructions, when executed, causethe STA to pad with the one or more PHY padding blocks each data unit ofthe plurality of data units, which is shorter than a longest data unitof the plurality of data units.
 20. The product of claim 17, wherein theMU PPDU comprises a Training (TRN) field after the data field.
 21. Anapparatus comprising logic and circuitry configured to cause a firstwireless communication station (STA) to: receive a Multi-User (MU)Physical Layer Protocol Data Unit (PPDU) from a second STA over achannel bandwidth in a frequency band above 45 Gigahertz (GHz), the MUPPDU comprising a first header (L-header) field decodable by DirectionalMulti-Gigabit (DMG) stations, a second header (Header A) field after theL-header field, a third header (Header B) field after the Header Afield, and a data field after the Header B field, the data fieldcomprising a plurality of data units to a plurality of users, theplurality of data units comprising a data unit for the first STA; basedat least on the Header B field, determine that the data unit for thefirst STA is padded with one or more PHY padding blocks to align saidplurality of data units in time; and process the data unit for the firstSTA.
 22. The apparatus of claim 21 configured to cause the first STA todetermine that the data unit for the first STA is padded with one ormore PHY padding blocks based at least on a length field in the Header Bfield.
 23. The apparatus of claim 21 configured to cause the first STAto determine a beginning of a Training (TRN) field after the data field.24. The apparatus of claim 21, wherein the data unit for the first STAcomprises an Aggregate Medium Access Control (MAC) Protocol Data Unit(A-MPDU).
 25. The apparatus of claim 21, wherein the channel bandwidthcomprises one or more 2.16 GHz channels.
 26. The apparatus of claim 25,wherein the Header A field comprises an indication of the one or more2.16 GHz channels.
 27. The apparatus of claim 25, wherein the channelbandwidth comprises a channel bandwidth of 4.32 GHz or 6.48 GHz.
 28. Theapparatus of claim 21, wherein the MU PPDU comprises an ExtendedDirectional Multi-Gigabit (EDMG) MU PPDU, the Header A field comprisesan EDMG Header A field, and the Header B field comprises an EDMG HeaderB field.
 29. The apparatus of claim 21 comprising a Medium AccessControl (MAC), and a Physical Layer (PHY).
 30. The apparatus of claim 21comprising a radio.
 31. The apparatus of claim 21 comprising one or moreantennas.
 32. An apparatus comprising: means for causing a firstwireless communication station (STA) to receive a Multi-User (MU)Physical Layer Protocol Data Unit (PPDU) from a second STA over achannel bandwidth in a frequency band above 45 Gigahertz (GHz), the MUPPDU comprising a first header (L-header) field decodable by DirectionalMulti-Gigabit (DMG) stations, a second header (Header A) field after theL-header field, a third header (Header B) field after the Header Afield, and a data field after the Header B field, the data fieldcomprising a plurality of data units to a plurality of users, theplurality of data units comprising a data unit for the first STA; meansfor determining, based at least on the Header B field, that the dataunit for the first STA is padded with one or more PHY padding blocks toalign said plurality of data units in time; and means for processing thedata unit for the first STA.
 33. The apparatus of claim 32 comprisingmeans for determining that the data unit for the first STA is paddedwith one or more PHY padding blocks based at least on a length field inthe Header B field.
 34. The apparatus of claim 32 comprising means fordetermining a beginning of a Training (TRN) field after the data field.